fix(ci): don't use pip3
to install awscli
#3786
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current
stable
CI is almost perfect except it gives this error onmacos-14
:This is actions/runner-images#8615; it so happened that when we were releasing v1.27.0,
pip3
was on Python v3.11, so that didn't bring up any error message.Since
awscli
is already bundled inmacos-(12|14)
andubuntu-*
,pip3 install awscli
actually has no effect. I think it’d be better to make the installation line a version check instead.For
windows
runners, the existingawscli
is alreadychoco
-managed, so there's nothing to be done.It's worth noticing that the preinstalled
awscli
is on v2, but onpip
we have awscli 1.32.89 as the latest version. However, given that we've already used the v2 for release purposes unintentionally for quite a while now, the differences here regarding the specificaws s3 cp
command should be minimal.This fix cannot be properly tested since it touches some part of the release process, but the
aws --version
part has been tested and is guaranteed to work.